Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Generating the configuration file

The configuration file defines the environment in which a Progress Dynamics installation can run. The definition of each session type includes the following startup information:

All of its required startup parameters (session properties).
Its logical and physical resources (session services).
The management procedures (Progress Dynamics managers) with which it runs.

The configuration file is used solely by the Configuration File Manager. The main purpose of the configuration file is to allow a centralized point where you can place various different sessions’ configuration parameters so that they are accessible anywhere on the network. Multiple clients can use the same configuration file. The configuration file is an XML file that can be read across the network because of built-in features of the XML Document Object Model (DOM).

When you install Progress Dynamics, the Progress Dynamics Configuration Utility (DCU) places a default configuration file called icfconfig.xml in OpenEdge-Install-Dir/src/dynamics. (For a detailed description of the contents of the default icfconfig.xml, see Appendix C "Inside the Progress Dynamics Configuration File.") This default configuration file lets you initially start Progress Dynamics so you can access the Progress Dynamics tools to define your own sessions and create your own configuration file.

When you start Progress Dynamics for the first time, you should create a new configuration file in your working directory. In general, you should not edit your configuration XML file manually (in an XML or text editor). You should instead use the framework’s administration tools to generate the files. The tools allow you to include only the session types you want in a given configuration file.

When you save the information that you add or change in the Session Type Control window, that information is saved into the Repository. To place those settings into the configuration file, you must generate (or regenerate) the XML file.

To complete the example, you can generate a configuration file for the DynSports session type.

To generate (or regenerate) your configuration XML file:

From the Administration window, choose Session Generate Configuration file. The Generate Configuration XML file window appears, as shown:



Choose Local File. Because the configuration file is in XML format, you can deploy it on a local disk or remotely, on a Universal Naming Convention (UNC) share or on a Web server. Generating it for remote use allows you to centralize the administration and set up of your application environment and reduces deployment issues.
Type DynSportsConfig.xml for the File Name. If you want the file to be stored somewhere other than in the OpenEdge-Install-Dir/src/dynamics directory, use the Browse button to set the appropriate path. The directory should be listed in your PROPATH.
Clear the Minimum XML toggle box, if necessary. The Minimum XML setting is a security measure. For more information, see the "Using minimum XML files" section.
Select DynSports in the Available Session Types list, then choose ADD> in order to move it to the Selected Session Types list.
Select the Generate button. Progress Dynamics only selects the session types in the Selected Session Types list to include in the generated configuration file.
When the message appears stating that the configuration file was successfully saved, select OK to dismiss the message dialog box.